The Chocolatey cppcheck package is broken - it was compiled with a
hardcoded FILESDIR path that doesn't exist on GitHub Actions runners:

  "Failed to load std.cfg. The Cppcheck binary was compiled with
   FILESDIR set to R:/winlibs64ucrt_stage/inst_cppcheck-2.14.0/share/Cppcheck"

The official cppcheck project marks the Chocolatey package as outdated
and recommends using Scoop instead. This change:
- Installs cppcheck via Scoop instead of Chocolatey
- Adds Scoop shims directory to PATH for the job

The PROFILE was running Enter-VsDevShell in every PowerShell step,
resetting PATH each time and overriding the Python set by setup-python.

Now VsDevShell setup only runs in the Prepare env step itself.

…hell

The ilammy/msvc-dev-cmd action already sets up MSVC environment and
exports it to GITHUB_ENV before setup-python runs. The manual
Enter-VsDevShell call was redundant and caused PATH conflicts.

The Update-SessionEnvironment call from chocolatey was overwriting
MSVC environment variables set by ilammy/msvc-dev-cmd. By moving
the MSVC dev command step after chocolatey packages are installed,
we ensure the MSVC environment persists to subsequent steps.

Co-authored-by: Claude <noreply@anthropic.com>

* Fix Windows CI: restore Python PATH after MSVC setup

The ilammy/msvc-dev-cmd action runs vcvarsall.bat which prepends
Visual Studio paths to PATH. VS 2022 includes a bundled Python 3.9,
which then takes precedence over the Python 3.10+ set up by
actions/setup-python.

This caused pre-commit to use Python 3.9 when installing the
cmake-pre-commit-hooks package, which fails because the package
requires Python 3.10+.

Fix by adding a step after msvc-dev-cmd that writes the correct
Python path to GITHUB_PATH, ensuring it's prepended in subsequent
steps.

* Add debugging for Windows Python PATH verification

Add a step to verify which Python and pre-commit are being used
after the PATH restoration to help diagnose CI failures.

* Fix Windows CI: ensure python3 points to correct Python

Pre-commit looks for 'python3' when creating virtualenvs for hooks.
After MSVC dev cmd runs, 'python3' might point to VS's bundled Python 3.9
instead of the Python 3.10+ from actions/setup-python.

This fix:
1. Creates python3.exe as a copy of python.exe if it doesn't exist
2. Uses a fresh PRE_COMMIT_HOME to avoid cached environments
3. Adds detailed PATH debugging to diagnose issues

* Fix Windows CI: restore Python PATH after Update-SessionEnvironment

The chocolatey Update-SessionEnvironment command resets PATH from
system environment variables, which overwrites the Python path set
by actions/setup-python. This caused pip to install packages into
Python 3.9.13 (system Python) instead of Python 3.12.10.

Fix by explicitly restoring pythonLocation to PATH immediately after
Update-SessionEnvironment, before running pip install.

* Remove debugging code from Windows CI

---------

Co-authored-by: Claude <noreply@anthropic.com>